Skip to content

feat: Expose session api#199

Draft
Takaros999 wants to merge 6 commits into
mainfrom
takis/expose-session-api
Draft

feat: Expose session api#199
Takaros999 wants to merge 6 commits into
mainfrom
takis/expose-session-api

Conversation

@Takaros999
Copy link
Copy Markdown
Contributor

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
idkit-js-example Ready Ready Preview, Comment May 22, 2026 2:12pm

Request Review

@Takaros999 Takaros999 force-pushed the takis/expose-session-api branch from bfa3d33 to 00ab31a Compare May 22, 2026 12:56
@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 22, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: Brillig: Heap corruption in foreign call results with nested tuple arrays

CVE: GHSA-jj7c-x25r-r8r3 Brillig: Heap corruption in foreign call results with nested tuple arrays (CRITICAL)

Affected versions: < 1.0.0-beta.19

Patched version: 1.0.0-beta.19

From: ?cargo/world-id-primitives@0.11.0cargo/brillig@1.0.0-beta.11

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/brillig@1.0.0-beta.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: cargo lzma-sys under GPL-2.0+

License: GPL-2.0+ - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)

License: GPL-2.0-or-later - the applicable license policy does not allow this license (4) (lzma-sys-0.1.20/xz-5.2/COPYING)

License: GPL-3.0-or-later - the applicable license policy does not allow this license (4) (lzma-sys-0.1.20/xz-5.2/COPYING)

License: GPL-2.0-only - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)

License: GPL-3.0 - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING)

License: GPL-2.0+ - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING.GPLv2)

License: GPL-3.0 - The applicable license policy does not permit this license (5) (lzma-sys-0.1.20/xz-5.2/COPYING.GPLv3)

From: ?cargo/world-id-primitives@0.11.0cargo/lzma-sys@0.1.20

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/lzma-sys@0.1.20. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant